User and device authentication in enterprise systems

ABSTRACT

Methods and systems for authenticating users of client devices to allow access of resources and services in enterprise systems are described herein. An authentication device may validate a user based on authentication credentials received from a client device. Validation data stored by the authentication device, and a corresponding access token transmitted to the client device, may be used to authenticate the user for future resource access requests. A user secret also may be stored by the authentication device and used to validate the user for future resource access requests. Additionally, after validating a user with a first set of authentication credentials, additional sets of credentials for the user may be retrieved and stored at an access gateway for future requests to access other services or resources in an enterprise system.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 13/886,518, filed May 3, 2013, and entitled “USERAND DEVICE AUTHENTICATION IN ENTERPRISE SYSTEMS,” the disclosure ofwhich is incorporated by reference herein in its entirety and made parthereof.

FIELD

Aspects described herein generally relate to authentication of userswithin enterprise systems. More specifically, certain aspects hereinprovide approaches to securely authenticate users on mobile devices andother client devices to various resources and services in enterprisesystems.

BACKGROUND

Mobile devices, such as smart phones, personal digital assistants,tablet computers, other types of mobile computing devices, are becomingincreasingly popular. Mobile devices are used in personal and businesssettings for a variety of purposes. Additionally, many people havemultiple computing devices, including one or more mobile devices. Auser's different devices may be in different locations and may havedifferent physical device capabilities. For example, a user may have adesktop computer with a standard keyboard and mouse interface, a mobiledevice with a touch screen interface and voice recognition capabilities,a laptop computer with a fingerprint scanner interface, and so on.

Users with multiple computing devices may desire to access the samedata, applications, and other information using any of their devices. Inorder to access data and applications remotely via a client device, theuser may first be authenticated by an authentication service and/or aremote resource or service providing the data and applications.Typically, a user enters authentication credentials, such as a usernameand password, into their device in order to validate their identity andaccess the remote resources or services of an enterprise system. Usersmay be required to re-authenticate periodically, for example, duringcommunication sessions or at the beginning of a new session.Additionally, a single user may have different sets of authenticationcredentials for different remote resources or services.

BRIEF SUMMARY

The following presents a simplified summary of various aspects describedherein. This summary is not an extensive overview, and is not intendedto identify key or critical elements or to delineate the scope of theclaims. The following summary merely presents some concepts in asimplified form as an introductory prelude to the more detaileddescription provided below.

To overcome limitations in the prior art described above, and toovercome other limitations that will be apparent upon reading andunderstanding the present specification, aspects described herein aredirected towards secure authentication of users on mobile devices andother client devices, and allowing access to various resources andservices in enterprise systems. According to certain aspects, anauthentication device may receive user authentication credentials,including a password (or token), from a client device. The user may bevalidated with the authentication credentials, and the authenticationdevice may create validation data comprising the encrypted user passwordand an access token comprising the cryptographic key used to encrypt thepassword. The validation data may be stored by the authenticationdevice, and the access token may be transmitted to the client device.For future resource access requests from the client device, the clientdevice may transmit the access token, and the authentication device mayretrieve and decrypt the validation data using the access token receivedfrom the client device.

According to additional aspects, a user may input a user secret, forexample, a personal identification number, touch screen gesture, orbiometric data, via an input interface of the client device. The usersecret may be stored by the authentication device and used to validatefuture requests from the client device. For example, the user mayre-enter the user secret for future requests, and the authenticationdevice may compare the user secret in the request to the previouslystored user secret corresponding to the same user, device, and/orrequested resources or services.

According to further aspects, after validating a user with a first setof authentication credentials, one or more additional sets ofauthentication credentials may be retrieved for the first user andstored at an access gateway or other storage in an enterprise system.The additional sets of authentication credentials may correspond todifferent credentials of the same user for accessing various services orresources in the enterprise system. In future requests from the clientdevice, the user may be validated based on the first set ofauthentication credentials, and then an additional set of authenticationcredentials may be retrieved and injected to the request depending onthe requested service or resource.

These and additional aspects will be appreciated with the benefit of thedisclosures discussed in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of aspects described herein and theadvantages thereof may be acquired by referring to the followingdescription in consideration of the accompanying drawings, in which likereference numbers indicate like features, and wherein:

FIG. 1 depicts an illustrative computer system architecture that may beused in accordance with one or more illustrative aspects describedherein.

FIG. 2 depicts an illustrative remote-access system architecture thatmay be used in accordance with one or more illustrative aspectsdescribed herein.

FIG. 3 depicts an illustrative enterprise mobility management system inaccordance with one or more illustrative aspects described herein.

FIG. 4 depicts another illustrative enterprise mobility managementsystem in accordance with one or more illustrative aspects describedherein.

FIG. 5 is a flow diagram illustrating an example user authenticationprocess between a client device and an authentication device, inaccordance with one or more illustrative aspects described herein.

FIG. 6 is a flow diagram illustrating an example user authentication andresource access request between a client device and various componentsof an enterprise system, in accordance with one or more illustrativeaspects described herein.

FIGS. 7A and 7B are diagrams illustrating example techniques forcreating and using validation data and access tokens in anauthentication process between a client device and an authenticationdevice, in accordance with one or more illustrative aspects describedherein.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings identified above and which form a parthereof, and in which is shown by way of illustration various embodimentsin which aspects described herein may be practiced. It is to beunderstood that other embodiments may be utilized and structural andfunctional modifications may be made without departing from the scopedescribed herein. Various aspects are capable of other embodiments andof being practiced or being carried out in various different ways.

As a general introduction to the subject matter described in more detailbelow, aspects described herein are directed towards controlling remoteaccess to resources at an enterprise system using managed mobileapplications at mobile computing devices. An access manager may performa validation process that determines whether a mobile applicationrequesting access to enterprise resources has accurately identifieditself and has not been subsequently altered after installation at themobile computing device. In this way, the access manager may ensure themobile application requesting access to the enterprise resource can betrusted and is not attempting to circumvent the security mechanisms usedto protect those enterprise resources. As a result, individualsassociated with the enterprise may advantageously utilize enterpriseresources at their personal mobile devices.

It is to be understood that the phraseology and terminology used hereinare for the purpose of description and should not be regarded aslimiting. Rather, the phrases and terms used herein are to be giventheir broadest interpretation and meaning. The use of “including” and“comprising” and variations thereof is meant to encompass the itemslisted thereafter and equivalents thereof as well as additional itemsand equivalents thereof. The use of the terms “mounted,” “connected,”“coupled,” “positioned,” “engaged” and similar terms, is meant toinclude both direct and indirect mounting, connecting, coupling,positioning and engaging.

Computing Architecture

Computer software, hardware, and networks may be utilized in a varietyof different system environments, including standalone, networked,remote-access (aka, remote desktop), virtualized, and/or cloud-basedenvironments, among others. FIG. 1 illustrates one example of a systemarchitecture and data processing device that may be used to implementone or more illustrative aspects described herein in a standalone and/ornetworked environment. Various network nodes 103, 105, 107, and 109 maybe interconnected via a wide area network (WAN) 101, such as theInternet. Other networks may also or alternatively be used, includingprivate intranets, corporate networks, LANs, metropolitan area networks(MANs) wireless networks, personal networks (PANs), and the like.Network 101 is for illustration purposes and may be replaced with feweror additional computer networks. A local area network (LAN) may have oneor more of any known LAN topology and may use one or more of a varietyof different protocols, such as Ethernet. Devices 103, 105, 107, 109 andother devices (not shown) may be connected to one or more of thenetworks via twisted pair wires, coaxial cable, fiber optics, radiowaves or other communication media.

The term “network” as used herein and depicted in the drawings refersnot only to systems in which remote storage devices are coupled togethervia one or more communication paths, but also to stand-alone devicesthat may be coupled, from time to time, to such systems that havestorage capability. Consequently, the term “network” includes not only a“physical network” but also a “content network,” which is comprised ofthe data—attributable to a single entity—which resides across allphysical networks.

The components may include data server 103, web server 105, and clientcomputers 107, 109. Data server 103 provides overall access, control andadministration of databases and control software for performing one ormore illustrative aspects described herein. Data server 103 may beconnected to web server 105 through which users interact with and obtaindata as requested. Alternatively, data server 103 may act as a webserver itself and be directly connected to the Internet. Data server 103may be connected to web server 105 through the network 101 (e.g., theInternet), via direct or indirect connection, or via some other network.Users may interact with the data server 103 using remote computers 107,109, e.g., using a web browser to connect to the data server 103 via oneor more externally exposed web sites hosted by web server 105. Clientcomputers 107, 109 may be used in concert with data server 103 to accessdata stored therein, or may be used for other purposes. For example,from client device 107, a user may access web server 105 using anInternet browser, as is known in the art, or by executing a softwareapplication that communicates with web server 105 and/or data server 103over a computer network (such as the Internet).

Servers and applications may be combined on the same physical machines,and retain separate virtual or logical addresses, or may reside onseparate physical machines. FIG. 1 illustrates just one example of anetwork architecture that may be used, and those of skill in the artwill appreciate that the specific network architecture and dataprocessing devices used may vary, and are secondary to the functionalitythat they provide, as further described herein. For example, servicesprovided by web server 105 and data server 103 may be combined on asingle server.

Each component 103, 105, 107, 109 may be any type of known computer,server, or data processing device. Data server 103, e.g., may include aprocessor 111 controlling overall operation of the data server 103. Dataserver 103 may further include RAM 113, ROM 115, network interface 117,input/output interfaces 119 (e.g., keyboard, mouse, display, printer,etc.), and memory 121. I/O 119 may include a variety of interface unitsand drives for reading, writing, displaying, and/or printing data orfiles. Memory 121 may further store operating system software 123 forcontrolling overall operation of the data processing device 103, controllogic 125 for instructing data server 103 to perform aspects describedherein, and other application software 127 providing secondary, support,and/or other functionality which may or may not be used in conjunctionwith aspects described herein. The control logic may also be referred toherein as the data server software 125. Functionality of the data serversoftware may refer to operations or decisions made automatically basedon rules coded into the control logic, made manually by a user providinginput into the system, and/or a combination of automatic processingbased on user input (e.g., queries, data updates, etc.).

Memory 121 may also store data used in performance of one or moreaspects described herein, including a first database 129 and a seconddatabase 131. In some embodiments, the first database may include thesecond database (e.g., as a separate table, report, etc.). That is, theinformation can be stored in a single database, or separated intodifferent logical, virtual, or physical databases, depending on systemdesign. Devices 105, 107, 109 may have similar or different architectureas described with respect to device 103. Those of skill in the art willappreciate that the functionality of data processing device 103 (ordevice 105, 107, 109) as described herein may be spread across multipledata processing devices, for example, to distribute processing loadacross multiple computers, to segregate transactions based on geographiclocation, user access level, quality of service (QoS), etc.

One or more aspects may be embodied in computer-usable or readable dataand/or computer-executable instructions, such as in one or more programmodules, executed by one or more computers or other devices as describedherein. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other device. The modules may be written in a source codeprogramming language that is subsequently compiled for execution, or maybe written in a scripting language such as (but not limited to) HTML orXML. The computer executable instructions may be stored on a computerreadable medium such as a nonvolatile storage device. Any suitablecomputer readable storage media may be utilized, including hard disks,CD-ROMs, optical storage devices, magnetic storage devices, and/or anycombination thereof. In addition, various transmission (non-storage)media representing data or events as described herein may be transferredbetween a source and a destination in the form of electromagnetic wavestraveling through signal-conducting media such as metal wires, opticalfibers, and/or wireless transmission media (e.g., air and/or space).Various aspects described herein may be embodied as a method, a dataprocessing system, or a computer program product. Therefore, variousfunctionalities may be embodied in whole or in part in software,firmware and/or hardware or hardware equivalents such as integratedcircuits, field programmable gate arrays (FPGA), and the like.Particular data structures may be used to more effectively implement oneor more aspects described herein, and such data structures arecontemplated within the scope of computer executable instructions andcomputer-usable data described herein.

With further reference to FIG. 2, one or more aspects described hereinmay be implemented in a remote-access environment. FIG. 2 depicts anexample system architecture including a generic computing device 201 inan illustrative computing environment 200 that may be used according toone or more illustrative aspects described herein. For example, genericcomputing device 201 may be used as a server 206 a in a single-server ormulti-server desktop virtualization system (e.g., a remote access orcloud system) configured to provide virtual machines for client accessdevices. The generic computing device 201 may have a processor 203 forcontrolling overall operation of the server and its associatedcomponents, including random access memory (RAM) 205, read-only memory(ROM) 207, input/output (I/O) module 209, and memory 215.

I/O module 209 may include a mouse, keypad, touch screen, scanner,optical reader, and/or stylus (or other input device(s)) through which auser of generic computing device 201 may provide input, and may alsoinclude one or more of a speaker for providing audio output and a videodisplay device for providing textual, audiovisual, and/or graphicaloutput. Software may be stored within memory 215 and/or other storage toprovide instructions to processor 203 for configuring generic computingdevice 201 into a special purpose computing device in order to performvarious functions as described herein. For example, memory 215 may storesoftware used by the computing device 201, such as an operating system217, application programs 219, and an associated database 221.

Computing device 201 may operate in a networked environment supportingconnections to one or more remote computers, such as terminals 240 (alsoreferred to as client devices). The terminals 240 may be personalcomputers, mobile devices, laptop computers, tablets, or servers thatinclude many or all of the elements described above with respect to thegeneric computing device 103 or 201. The network connections depicted inFIG. 2 include a local area network (LAN) 225 and a wide area network(WAN) 229, but may also include other networks. When used in a LANnetworking environment, computing device 201 may be connected to the LAN225 through a network interface or adapter 223. When used in a WANnetworking environment, computing device 201 may include a modem 227 orother wide area network interface for establishing communications overthe WAN 229, such as computer network 230 (e.g., the Internet). It willbe appreciated that the network connections shown are illustrative andother means of establishing a communications link between the computersmay be used. Computing device 201 and/or terminals 240 may also bemobile terminals (e.g., mobile phones, smartphones, PDAs, notebooks,etc.) including various other components, such as a battery, speaker,and antennas (not shown).

Aspects described herein may also be operational with numerous othergeneral purpose or special purpose computing system environments orconfigurations. Examples of other computing systems, environments,and/or configurations that may be suitable for use with aspectsdescribed herein include, but are not limited to, personal computers,server computers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of the above systemsor devices, and the like.

As shown in FIG. 2, one or more client devices 240 may be incommunication with one or more servers 206 a-206 n (generally referredto herein as “server(s) 206”). In one embodiment, the computingenvironment 200 may include a network appliance installed between theserver(s) 206 and client machine(s) 240. The network appliance maymanage client/server connections, and in some cases can load balanceclient connections amongst a plurality of backend servers 206.

The client machine(s) 240 may in some embodiments be referred to as asingle client machine 240 or a single group of client machines 240,while server(s) 206 may be referred to as a single server 206 or asingle group of servers 206. In one embodiment a single client machine240 communicates with more than one server 206, while in anotherembodiment a single server 206 communicates with more than one clientmachine 240. In yet another embodiment, a single client machine 240communicates with a single server 206.

A client machine 240 can, in some embodiments, be referenced by any oneof the following non-exhaustive terms: client machine(s); client(s);client computer(s); client device(s); client computing device(s); localmachine; remote machine; client node(s); endpoint(s); or endpointnode(s). The server 206, in some embodiments, may be referenced by anyone of the following non-exhaustive terms: server(s), local machine;remote machine; server farm(s), or host computing device(s).

In one embodiment, the client machine 240 may be a virtual machine. Thevirtual machine may be any virtual machine, while in some embodimentsthe virtual machine may be any virtual machine managed by a Type 1 orType 2 hypervisor, for example, a hypervisor developed by CitrixSystems, IBM, VMware, or any other hypervisor. In some aspects, thevirtual machine may be managed by a hypervisor, while in aspects thevirtual machine may be managed by a hypervisor executing on a server 206or a hypervisor executing on a client 240.

Some embodiments include a client device 240 that displays applicationoutput generated by an application remotely executing on a server 206 orother remotely located machine. In these embodiments, the client device240 may execute a virtual machine receiver program or application todisplay the output in an application window, a browser, or other outputwindow. In one example, the application is a desktop, while in otherexamples the application is an application that generates or presents adesktop. A desktop may include a graphical shell providing a userinterface for an instance of an operating system in which local and/orremote applications can be integrated. Applications, as used herein, areprograms that execute after an instance of an operating system (and,optionally, also the desktop) has been loaded.

The server 206, in some embodiments, uses a remote presentation protocolor other program to send data to a thin-client or remote-displayapplication executing on the client to present display output generatedby an application executing on the server 206. The thin-client orremote-display protocol can be any one of the following non-exhaustivelist of protocols: the Independent Computing Architecture (ICA) protocoldeveloped by Citrix Systems, Inc. of Ft. Lauderdale, Fla.; or the RemoteDesktop Protocol (RDP) manufactured by the Microsoft Corporation ofRedmond, Wash.

A remote computing environment may include more than one server 206a-206 n such that the servers 206 a-206 n are logically grouped togetherinto a server farm 206, for example, in a cloud computing environment.The server farm 206 may include servers 206 that are geographicallydispersed while and logically grouped together, or servers 206 that arelocated proximate to each other while logically grouped together.Geographically dispersed servers 206 a-206 n within a server farm 206can, in some embodiments, communicate using a WAN (wide), MAN(metropolitan), or LAN (local), where different geographic regions canbe characterized as: different continents; different regions of acontinent; different countries; different states; different cities;different campuses; different rooms; or any combination of the precedinggeographical locations. In some embodiments the server farm 206 may beadministered as a single entity, while in other embodiments the serverfarm 206 can include multiple server farms.

In some embodiments, a server farm may include servers 206 that executea substantially similar type of operating system platform (e.g.,WINDOWS, UNIX, LINUX, iOS, ANDROID, SYMBIAN, etc.) In other embodiments,server farm 206 may include a first group of one or more servers thatexecute a first type of operating system platform, and a second group ofone or more servers that execute a second type of operating systemplatform.

Server 206 may be configured as any type of server, as needed, e.g., afile server, an application server, a web server, a proxy server, anappliance, a network appliance, a gateway, an application gateway, agateway server, a virtualization server, a deployment server, a SSL VPNserver, a firewall, a web server, an application server or as a masterapplication server, a server executing an active directory, or a serverexecuting an application acceleration program that provides firewallfunctionality, application functionality, or load balancingfunctionality. Other server types may also be used.

Some embodiments include a first server 206 a that receives requestsfrom a client machine 240, forwards the requests to a second server 206b, and responds to the requests generated by the client machine 240 witha response from the second server 206 b. First server 206 a may acquirean enumeration of applications available to the client machine 240, aswell as address information associated with an application server 206hosting an application identified within the enumeration ofapplications. First server 206 a can then present a response to theclient's requests using a web interface, and communicate directly withthe client 240 to provide the client 240 with access to an identifiedapplication. One or more clients 240 and/or one or more servers 206 maytransmit data over network 230, e.g., network 101.

FIG. 2 shows a high-level architecture which may be illustrative of adesktop virtualization system. As shown, the desktop virtualizationsystem may be single-server or multi-server system, or cloud system,including at least one virtualization server 206 configured to providevirtual desktops and/or virtual applications to one or more clientaccess devices 240. As used herein, a desktop refers to a graphicalenvironment or space in which one or more applications may be hostedand/or executed. A desktop may include a graphical shell providing auser interface for an instance of an operating system in which localand/or remote applications can be integrated. Applications may includeprograms that execute after an instance of an operating system (and,optionally, also the desktop) has been loaded. Each instance of theoperating system may be physical (e.g., one operating system per device)or virtual (e.g., many instances of an OS running on a single device).Each application may be executed on a local device, or executed on aremotely located device (e.g., remoted).

When utilized in a desktop virtualization system, server 206 may beconfigured as virtualization server in a virtualization environment, forexample, a single-server, multi-server, or cloud computing environment.In such embodiments, the virtualization server 206 may include ahardware layer including one or more physical disks, physical devices,physical processors, and physical memories. The memory 215 of thevirtualization server 206 may include firmware, an operating system, anda hypervisor (e.g., a Type 1 or Type 2 hypervisor) configured to createand manage any number of virtual machines. A virtual machine is a set ofexecutable instructions that, when executed by a processor, imitate theoperation of a physical computer such that the virtual machine canexecute programs and processes much like a physical computing device.The hypervisor may provide each virtual machine with a virtual view ofthe physical hardware, memory, processor and other system resourcesavailable to that virtual machine.

Some aspects described herein may be implemented in a cloud-basedenvironment. In such environments, client devices 240 may communicatewith one or more cloud management servers 206 to access the computingresources (e.g., host servers, storage resources, and network resources)of the cloud system. Cloud management servers 206 may manage variouscomputing resources, including cloud hardware and software resources,and may provide user interfaces through which cloud operators and cloudcustomers may interact with the cloud system. For example, managementservers 206 may provide a set of APIs and/or one or more cloud operatorconsole applications (e.g., web-based or standalone applications) withuser interfaces to allow cloud operators to manage the cloud resources,configure the virtualization layer, manage customer accounts, andperform other cloud administration tasks. Management servers 206 alsomay include a set of APIs and/or one or more customer consoleapplications with user interfaces configured to receive cloud computingrequests from end users via client computers 240, for example, requeststo create, modify, or destroy virtual machines within the cloud. Clientcomputers 240 may connect to management server 206 via the Internet orother communication network, and may request access to one or more ofthe computing resources managed by management server 206. In response toclient requests, the management server 206 may include a resourcemanager configured to select and provision physical resources in thehardware layer of the cloud system based on the client requests. Forexample, the management server 206 and additional components of thecloud system may be configured to provision, create, and manage virtualmachines and their operating environments (e.g., hypervisors, storageresources, services offered by the network elements, etc.) for customersat client computers 240, over a network (e.g., the Internet), providingcustomers with computational resources, data storage services,networking capabilities, and computer platform and application support.Cloud systems also may be configured to provide various specificservices, including security systems, development environments, userinterfaces, and the like.

Cloud computing environments also may include a virtualization layerwith additional hardware and/or software resources configured to createand manage virtual machines and provide other services to customersusing the physical resources in the cloud. The virtualization layer mayinclude hypervisors, as described above, along with other components toprovide network virtualizations, storage virtualizations, etc. Thevirtualization layer may be as a separate layer from the physicalresource layer, or may share some or all of the same hardware and/orsoftware resources with the physical resource layer.

Enterprise Mobility Management Architecture

FIG. 3 represents an enterprise mobility technical architecture 300 foruse in a BYOD environment. The architecture enables a user of a mobiledevice 302 to both access enterprise or personal resources from a mobiledevice 302 and use the mobile device 302 for personal use. The user mayaccess such enterprise resources 304 or enterprise services 308 using amobile device 302 that is purchased by the user or a mobile device 302that is provided by the enterprise to the user. The user may utilize themobile device 302 for business use only or for business and personaluse. The mobile device may run an iOS operating system, an Androidoperating system, or the like. The enterprise may choose to implementpolicies to manage the mobile device 302. The policies may beimplemented through a firewall or gateway in such a way that the mobiledevice may be identified, secured or security verified, and providedselective or full access to the enterprise resources. The policies maybe mobile device management policies, mobile application managementpolicies, mobile data management policies, or some combination of mobiledevice, application, and data management policies. A mobile device 302that is managed through the application of mobile device managementpolicies may be referred to as an enrolled device.

The operating system of the mobile device may be separated into amanaged partition 310 and an unmanaged partition 312. The managedpartition 310 may have policies applied to it to secure the applicationsrunning on and data stored in the managed partition. The applicationsrunning on the managed partition may be secure applications. The secureapplications may be email applications, web browsing applications,software-as-a-service (SaaS) access applications, Windows Applicationaccess applications, and the like. The secure applications may be securenative applications 314, secure remote applications 322 executed by asecure application launcher 318, virtualization applications 326executed by a secure application launcher 318, and the like. The securenative applications 314 may be wrapped by a secure application wrapper320. The secure application wrapper 320 may include integrated policiesthat are executed on the mobile device 302 when the secure nativeapplication is executed on the device. The secure application wrapper320 may include meta-data that points the secure native application 314running on the mobile device 302 to the resources hosted at theenterprise that the secure native application 314 may require tocomplete the task requested upon execution of the secure nativeapplication 314. The secure remote applications 322 executed by a secureapplication launcher 318 may be executed within the secure applicationlauncher application 318. The virtualization applications 326 executedby a secure application launcher 318 may utilize resources on the mobiledevice 302, at the enterprise resources 304, and the like. The resourcesused on the mobile device 302 by the virtualization applications 326executed by a secure application launcher 318 may include userinteraction resources, processing resources, and the like. The userinteraction resources may be used to collect and transmit keyboardinput, mouse input, camera input, tactile input, audio input, visualinput, gesture input, and the like. The processing resources may be usedto present a user interface, process data received from the enterpriseresources 304, and the like. The resources used at the enterpriseresources 304 by the virtualization applications 326 executed by asecure application launcher 318 may include user interface generationresources, processing resources, and the like. The user interfacegeneration resources may be used to assemble a user interface, modify auser interface, refresh a user interface, and the like. The processingresources may be used to create information, read information, updateinformation, delete information, and the like. For example, thevirtualization application may record user interactions associated witha GUI and communicate them to a server application where the serverapplication will use the user interaction data as an input to theapplication operating on the server. In this arrangement, an enterprisemay elect to maintain the application on the server side as well asdata, files, etc. associated with the application. While an enterprisemay elect to “mobilize” some applications in accordance with theprinciples herein by securing them for deployment on the mobile device,this arrangement may also be elected for certain applications. Forexample, while some applications may be secured for use on the mobiledevice, others may not be prepared or appropriate for deployment on themobile device so the enterprise may elect to provide the mobile useraccess to the unprepared applications through virtualization techniques.As another example, the enterprise may have large complex applicationswith large and complex data sets (e.g. material resource planningapplications) where it would be very difficult, or otherwiseundesirable, to customize the application for the mobile device so theenterprise may elect to provide access to the application throughvirtualization techniques. As yet another example, the enterprise mayhave an application that maintains highly secured data (e.g. humanresources data, customer data, engineering data) that may be deemed bythe enterprise as too sensitive for even the secured mobile environmentso the enterprise may elect to use virtualization techniques to permitmobile access to such applications and data. An enterprise may elect toprovide both fully secured and fully functional applications on themobile device as well as a virtualization application to allow access toapplications that are deemed more properly operated on the server side.In an embodiment, the virtualization application may store some data,files, etc. on the mobile phone in one of the secure storage locations.An enterprise, for example, may elect to allow certain information to bestored on the phone while not permitting other information.

In connection with the virtualization application, as described herein,the mobile device may have a virtualization application that is designedto present GUI's and then record user interactions with the GUI. Theapplication may communicate the user interactions to the server side tobe used by the server side application as user interactions with theapplication. In response, the application on the server side maytransmit back to the mobile device a new GUI. For example, the new GUImay be a static page, a dynamic page, an animation, or the like.

The applications running on the managed partition may be stabilizedapplications. The stabilized applications may be managed by a devicemanager 324. The device manager 324 may monitor the stabilizedapplications and utilize techniques for detecting and remedying problemsthat would result in a destabilized application if such techniques werenot utilized to detect and remedy the problems.

The secure applications may access data stored in a secure datacontainer 328 in the managed partition 310 of the mobile device. Thedata secured in the secure data container may be accessed by the securewrapped applications 314, applications executed by a secure applicationlauncher 322, virtualization applications 326 executed by a secureapplication launcher 322, and the like. The data stored in the securedata container 328 may include files, databases, and the like. The datastored in the secure data container 328 may include data restricted to aspecific secure application 330, shared among secure applications 332,and the like. Data restricted to a secure application may include securegeneral data 334 and highly secure data 338. Secure general data may usea strong form of encryption such as AES 128-bit encryption or the like,while highly secure data 338 may use a very strong form of encryptionsuch as AES 254-bit encryption. Data stored in the secure data container328 may be deleted from the device upon receipt of a command from thedevice manager 324. The secure applications may have a dual-mode option340. The dual mode option 340 may present the user with an option tooperate the secured application in an unsecured mode. In an unsecuredmode, the secure applications may access data stored in an unsecureddata container 342 on the unmanaged partition 312 of the mobile device302. The data stored in an unsecured data container may be personal data344. The data stored in an unsecured data container 342 may also beaccessed by unsecured applications 348 that are running on the unmanagedpartition 312 of the mobile device 302. The data stored in an unsecureddata container 342 may remain on the mobile device 302 when the datastored in the secure data container 328 is deleted from the mobiledevice 302. An enterprise may want to delete from the mobile deviceselected or all data, files, and/or applications owned, licensed orcontrolled by the enterprise (enterprise data) while leaving orotherwise preserving personal data, files, and/or applications owned,licensed or controlled by the user (personal data). This operation maybe referred to as a selective wipe. With the enterprise and personaldata arranged in accordance to the aspects described herein, anenterprise may perform a selective wipe.

The mobile device may connect to enterprise resources 304 and enterpriseservices 308 at an enterprise, to the public Internet 348, and the like.The mobile device may connect to enterprise resources 304 and enterpriseservices 308 through virtual private network connections. The virtualprivate network connections 352 may be specific to particularapplications 350, particular devices, particular secured areas on themobile device, and the like. For example, each of the wrappedapplications in the secured area of the phone may access enterpriseresources through an application specific VPN such that access to theVPN would be granted based on attributes associated with theapplication, possibly in conjunction with user or device attributeinformation. The virtual private network connections may carry MicrosoftExchange traffic, Microsoft Active Directory traffic, HTTP traffic,HTTPS traffic, application management traffic, and the like. The virtualprivate network connections may support and enable single-sign-onauthentication processes 354. The single-sign-on processes may allow auser to provide a single set of authentication credentials, which arethen verified by an authentication service 358. The authenticationservice 358 may then grant to the user access to multiple enterpriseresources 304, without requiring the user to provide authenticationcredentials to each individual enterprise resource 304.

The virtual private network connections may be established and managedby an access gateway 360. The access gateway 360 may include performanceenhancement features that manage, accelerate, and improve the deliveryof enterprise resources 304 to the mobile device 302. The access gatewaymay also re-route traffic from the mobile device 302 to the publicInternet 348, enabling the mobile device 302 to access publiclyavailable and unsecured applications that run on the public Internet348. The mobile device may connect to the access gateway via a transportnetwork 362. The transport network 362 may be a wired network, wirelessnetwork, cloud network, local area network, metropolitan area network,wide area network, public network, private network, and the like.

The enterprise resources 304 may include email servers, file sharingservers, SaaS applications, Web application servers, Windows applicationservers, and the like. Email servers may include Exchange servers, LotusNotes servers, and the like. File sharing servers may include ShareFileservers, and the like. SaaS applications may include Salesforce, and thelike. Windows application servers may include any application serverthat is built to provide applications that are intended to run on alocal Windows operating system, and the like. The enterprise resources304 may be premise-based resources, cloud based resources, and the like.The enterprise resources 304 may be accessed by the mobile device 302directly or through the access gateway 360. The enterprise resources 304may be accessed by the mobile device 302 via a transport network 362.The transport network 362 may be a wired network, wireless network,cloud network, local area network, metropolitan area network, wide areanetwork, public network, private network, and the like.

The enterprise services 308 may include authentication services 358,threat detection services 364, device manager services 324, file sharingservices 368, policy manager services 370, social integration services372, application controller services 374, and the like. Authenticationservices 358 may include user authentication services, deviceauthentication services, application authentication services, dataauthentication services and the like. Authentication services 358 mayuse certificates. The certificates may be stored on the mobile device302, by the enterprise resources 304, and the like. The certificatesstored on the mobile device 302 may be stored in an encrypted locationon the mobile device, the certificate may be temporarily stored on themobile device 302 for use at the time of authentication, and the like.Threat detection services 364 may include intrusion detection services,unauthorized access attempt detection services, and the like.Unauthorized access attempt detection services may include unauthorizedattempts to access devices, applications, data, and the like. Devicemanagement services 324 may include configuration, provisioning,security, support, monitoring, reporting, and decommissioning services.File sharing services 368 may include file management services, filestorage services, file collaboration services, and the like. Policymanager services 370 may include device policy manager services,application policy manager services, data policy manager services, andthe like. Social integration services 372 may include contactintegration services, collaboration services, integration with socialnetworks such as Facebook, Twitter, and LinkedIn, and the like.Application controller services 374 may include management services,provisioning services, deployment services, assignment services,revocation services, wrapping services, and the like.

The enterprise mobility technical architecture 300 may include anapplication store 378. The application store 378 may include unwrappedapplications 380, pre-wrapped applications 382, and the like.Applications may be populated in the application store 378 from theapplication controller 374. The application store 378 may be accessed bythe mobile device 302 through the access gateway 360, through the publicInternet 348, or the like. The application store may be provided with anintuitive and easy to use User Interface. The application store 378 mayprovide access to a software development kit 384. The softwaredevelopment kit 384 may provide a user the capability to secureapplications selected by the user by wrapping the application asdescribed previously in this description. An application that has beenwrapped using the software development kit 384 may then be madeavailable to the mobile device 302 by populating it in the applicationstore 378 using the application controller 374.

The enterprise mobility technical architecture 300 may include amanagement and analytics capability. The management and analyticscapability may provide information related to how resources are used,how often resources are used, and the like. Resources may includedevices, applications, data, and the like. How resources are used mayinclude which devices download which applications, which applicationsaccess which data, and the like. How often resources are used mayinclude how often an application has been downloaded, how many times aspecific set of data has been accessed by an application, and the like.

FIG. 4 is another illustrative enterprise mobility management system400. Some of the components of the mobility management system 300described above with reference to FIG. 3 have been omitted for the sakeof simplicity. The architecture of the system 400 depicted in FIG. 4 issimilar in many respects to the architecture of the system 300 describedabove with reference to FIG. 3 and may include additional features notmentioned above.

In this case, the left hand side represents an enrolled mobile device402 with a receiver 404, which interacts with cloud gateway 406 (whichincludes access gateway and application controller functionality) toaccess various enterprise resources 408 and services 409 such asExchange, Sharepoint, PKI Resources, Kerberos Resources, CertificateIssuance service, as shown on the right hand side above. Although notspecifically shown, the mobile device 402 may also interact with anenterprise application store (e.g., StoreFront) for the selection anddownloading of applications.

The receiver 404 acts as the UI (user interface) intermediary forWindows apps/desktops hosted in an Enterprise data center, which areaccessed using the HDX/ICA display remoting protocol. The receiver 404also supports the installation and management of native applications onthe mobile device 402, such as native iOS or Android applications. Forexample, the managed applications 410 (mail, browser, wrappedapplication) shown in FIG. 4 above are all native applications thatexecute locally on the device. Receiver 404 and MDX (mobile experiencetechnology) of this architecture act to provide policy driven managementcapabilities and features such as connectivity and SSO (single sign on)to enterprise resources/services 408. The receiver 404 handles primaryuser authentication to the enterprise, normally to the access gateway(AG) with SSO to other cloud gateway components. The receiver 404obtains policies from cloud gateway 406 to control the behavior of theMDX managed applications 410 on the mobile device 402.

The secure IPC links 412 between the native applications 410 andreceiver 404 represent a management channel, which allows receiver 404to supply policies to be enforced by the MDX framework 414 “wrapping”each application. The IPC channel 412 also allows receiver 404 to supplycredential and authentication information that enables connectivity andSSO to enterprise resources 408. Finally the IPC channel 412 allows theMDX framework 414 to invoke user interface functions implemented byreceiver 404, such as online and offline authentication.

Communications between the receiver 404 and cloud gateway 406 areessentially an extension of the management channel from the MDXframework 414 wrapping each native managed application 410. The MDXframework 414 requests policy information from receiver 404, which inturn requests it from cloud gateway 406. The MDX framework 414 requestsauthentication, and receiver 404 logs into the gateway services part ofcloud gateway 406 (also known as NetScaler Access Gateway). Receiver 404may also call supporting services on cloud gateway 406, which mayproduce input material to derive encryption keys for the local datavaults 416, or provide client certificates which may enable directauthentication to PKI protected resources, as more fully explainedbelow.

In more detail, the MDX framework 414 “wraps” each managed application410. This may be incorporated via an explicit build step, or via apost-build processing step. The MDX framework 414 may “pair” withreceiver 404 on first launch of an application 410 to initialize thesecure IPC channel and obtain the policy for that application. The MDXframework 414 may enforce relevant portions of the policy that applylocally, such as the receiver login dependencies and some of thecontainment policies that restrict how local OS services may be used, orhow they may interact with the application 410.

The MDX framework 414 may use services provided by receiver 404 over thesecure IPC channel 412 to facilitate authentication and internal networkaccess. Key management for the private and shared data vaults 416(containers) may be also managed by appropriate interactions between themanaged applications 410 and receiver 404. Vaults 416 may be availableonly after online authentication, or may be made available after offlineauthentication if allowed by policy. First use of vaults 416 may requireonline authentication, and offline access may be limited to at most thepolicy refresh period before online authentication is again required.

Network access to internal resources may occur directly from individualmanaged applications 410 through the access gateway 406. The MDXframework 414 is responsible for orchestrating the network access onbehalf of each application 410. Receiver 404 may facilitate thesenetwork connections by providing suitable time limited secondarycredentials obtained following online authentication. Multiple modes ofnetwork connection may be used, such as reverse web proxy connectionsand end-to-end VPN-style tunnels 418.

The mail and browser managed applications 410 have special status andmay make use of facilities that might not be generally available toarbitrary wrapped applications. For example, the mail application mayuse a special background network access mechanism that allows it toaccess Exchange over an extended period of time without requiring a fullAD logon. The browser application may use multiple private data vaultsto segregate different kinds of data.

This architecture supports the incorporation of various other securityfeatures. For example, cloud gateway 406 (including its gatewayservices) in some cases will not need to validate AD passwords. It canbe left to the discretion of an enterprise whether an AD password isused as an authentication factor for some users in some situations.Different authentication methods may be used if a user is online oroffline (i.e., connected or not connected to a network).

Step up authentication is a feature wherein cloud gateway 406 mayidentify managed native applications 410 that are allowed to have accessto highly classified data requiring strong authentication, and ensurethat access to these applications is only permitted after performingappropriate authentication, even if this means a re-authentication isrequired by the user after a prior weaker level of login.

Another security feature of this solution is the encryption of the datavaults 416 (containers) on the mobile device 402. The vaults 416 may beencrypted so that all on-device data including files, databases, andconfigurations are protected. For on-line vaults, the keys may be storedon the server (cloud gateway 406), and for off-line vaults, a local copyof the keys may be protected by a user password. When data is storedlocally on the device 402 in the secure container 416, it is preferredthat a minimum of AES 256 encryption algorithm be utilized.

Other secure container features may also be implemented. For example, alogging feature may be included, wherein all security events happeninginside an application 410 are logged and reported to the backend. Datawiping may be supported, such as if the application 410 detectstampering, associated encryption keys may be written over with randomdata, leaving no hint on the file system that user data was destroyed.Screenshot protection is another feature, where an application mayprevent any data from being stored in screenshots. For example, the keywindow's hidden property may be set to YES. This may cause whatevercontent is currently displayed on the screen to be hidden, resulting ina blank screenshot where any content would normally reside.

Local data transfer may be prevented, such as by preventing any datafrom being locally transferred outside the application container, e.g.,by copying it or sending it to an external application. A keyboard cachefeature may operate to disable the autocorrect functionality forsensitive text fields. SSL certificate validation may be operable so theapplication specifically validates the server SSL certificate instead ofit being stored in the keychain. An encryption key generation featuremay be used such that the key used to encrypt data on the device isgenerated using a passphrase supplied by the user (if offline access isrequired). It may be XORed with another key randomly generated andstored on the server side if offline access is not required. Keyderivation functions may operate such that keys generated from the userpassword use KDFs (key derivation functions, notably PBKDF2) rather thancreating a cryptographic hash of it. The latter makes a key susceptibleto brute force or dictionary attacks.

Further, one or more initialization vectors may be used in encryptionmethods. An initialization vector will cause multiple copies of the sameencrypted data to yield different cipher text output, preventing bothreplay and cryptanalytic attacks. This will also prevent an attackerfrom decrypting any data even with a stolen encryption key if thespecific initialization vector used to encrypt the data is not known.Further, authentication then decryption may be used, wherein applicationdata is decrypted only after the user has authenticated within theapplication. Another feature may relate to sensitive data in memory,which may be kept in memory (and not in disk) only when it's needed. Forexample, login credentials may be wiped from memory after login, andencryption keys and other data inside objective-C instance variables arenot stored, as they may be easily referenced. Instead, memory may bemanually allocated for these.

An inactivity timeout may be implemented, wherein after a policy-definedperiod of inactivity, a user session is terminated.

Data leakage from the MDX framework 614 may be prevented in other ways.For example, when an application 610 is put in the background, thememory may be cleared after a predetermined (configurable) time period.When backgrounded, a snapshot may be taken of the last displayed screenof the application to fasten the foregrounding process. The screenshotmay contain confidential data and hence should be cleared.

Another security feature relates to the use of an OTP (one timepassword) 420 without the use of an AD (active directory) 422 passwordfor access to one or more applications. In some cases, some users do notknow (or are not permitted to know) their AD password, so these usersmay authenticate using an OTP 420 such as by using a hardware OTP systemlike SecurID (OTPs may be provided by different vendors also, such asEntrust or Gemalto). In some cases, after a user authenticates with auser ID, a text is sent to the user with an OTP 420. In some cases, thismay be implemented only for online use, with a prompt being a singlefield.

An offline password may be implemented for offline authentication forthose applications 410 for which offline use is permitted via enterprisepolicy. For example, an enterprise may want the enterprise applicationstore to be accessed in this manner. In this case, the receiver 404 mayrequire the user to set a custom offline password and the AD password isnot used. Cloud gateway 406 may provide policies to control and enforcepassword standards with respect to the minimum length, character classcomposition, and age of passwords, such as described by the standardWindows Server password complexity requirements, although theserequirements may be modified.

Another feature relates to the enablement of a client side certificatefor certain applications 410 as secondary credentials (for the purposeof accessing PKI protected web resources via the MDX micro VPN feature).For example, an application such as @WorkMail may utilize such acertificate. In this case, certificate-based authentication usingActiveSync protocol may be supported, wherein a certificate from thereceiver 404 may be retrieved by cloud gateway 406 and used in akeychain. Each managed application may have one associated clientcertificate, identified by a label that is defined in cloud gateway 406.

Cloud gateway 406 may interact with an enterprise special purpose webservice to support the issuance of client certificates to allow relevantmanaged applications to authenticate to internal PKI protectedresources.

The receiver 404 and the MDX framework 414 may be enhanced to supportobtaining and using client certificates for authentication to internalPKI protected network resources. More than one certificate may besupported, such as to match various levels of security and/or separationrequirements. The certificates may be used by the mail and browsermanaged applications, and ultimately by arbitrary wrapped applications(provided those applications use web service style communicationpatterns where it is reasonable for the MDX framework to mediate HTTPSrequests).

MDX client certificate support on iOS may rely on importing a PKCS 12BLOB (Binary Large Object) into the iOS keychain in each managedapplication for each period of use. MDX client certificate support mayuse a HTTPS implementation with private in-memory key storage. Theclient certificate will never be present in the iOS keychain and willnot be persisted except potentially in “online-only” data value that isstrongly protected.

Mutual SSL may also be implemented to provide additional security byrequiring that a mobile device 402 is authenticated to the enterprise,and vice versa. Virtual smart cards for authentication to cloud gateway406 may also be implemented.

Both limited and full Kerberos support may be additional features. Thefull support feature relates to an ability to do full Kerberos login toAD 422, using an AD password or trusted client certificate, and obtainKerberos service tickets to respond to HTTP negotiate authenticationchallenges. The limited support feature relates to constraineddelegation in AFEE, where AFEE supports invoking Kerberos protocoltransition so it can obtain and use Kerberos service tickets (subject toconstrained delegation) in response to HTTP negotiate authenticationchallenges. This mechanism works in reverse web proxy (a.k.a. CVPN)mode, and when HTTP (but not HTTPS) connections are proxied in VPN andMicroVPN mode.

Another feature relates to application container locking and wiping,which may automatically occur upon jail-break or rooting detections, andoccur as a pushed command from administration console, and may include aremote wipe functionality even when an application 410 is not running.

A multi-site architecture or configuration of the enterprise applicationstore and the application controller may be supported that allows usersto be serviced from one of several different locations in case offailure.

In some cases, managed applications 410 may be allowed to access acertificate and private key via an API (example OpenSSL). Trustedmanaged applications 410 of an enterprise may be allowed to performspecific Public Key operations with an application's client certificateand private key. Various use cases may be identified and treatedaccordingly, such as when an application behaves like a browser and nocertificate access is required, when an application reads a certificatefor “who am I,” when an application uses the certificate to build asecure session token, and when an application uses private keys fordigital signing of important data (e.g. transaction log) or fortemporary data encryption.

User and Device Authentication in Enterprise Systems

FIGS. 5 and 6 are flow diagrams illustrating various examples offeatures and methods of authenticating client devices in enterprisesystems. The features and methods described below in reference to FIGS.5 and 6 may be performed by a computing device or combination ofdevices, such as the various computing devices and systems shown inFIGS. 1 and 2, and may be implemented within various different types ofenterprise systems, such as the illustrative mobility management systemsshown in FIGS. 3 and 4, or any other enterprise system (i.e., anycomputing device that requires authentication when providing access toresources). FIGS. 5 and 6 relate to authentication and resource accesscontrol by an enterprise system for users accessing the system viaremote client devices. For example, a user at a mobile device 302 or 402may communicate with an enterprise system through an access gateway 360or 406, provide authentication credentials to validate the user'sidentity, and then may request and access the various resources andservices of the enterprise system.

The various embodiments and examples described in reference to FIGS. 5and 6 may include several features and potential advantages forauthentication and resource access control to users in enterprisesystems. As described in more detail below, certain embodiments mayallow users to input authentication credentials less frequently intotheir devices, and in some cases a simplified user secret may be enteredinstead of the user's full authentication credentials (e.g.,username/password), which may provide convenience and time savings fordevice users, and particularly mobile device users. Additionally,increased flexibility may be provided for user authentication andresource access control functionality, whereby specific authenticationcredentials and/or authentication requests may be associated withspecific enterprise services and resources and/or specific time periods.Enterprise system security also may be enhanced in various embodimentsand examples, when secure credentials such as user passwords may beinput less frequently (or not at all) by the user, and need not bestored at the client device, thereby protecting the user and the systemin the event that the client device or communication network iscompromised.

Referring now to FIG. 5, an example method is shown in which a clientdevice (e.g., mobile device 302 and/or 402), and an authenticationdevice (e.g., authentication service 358 and/or cloud gateway 406)communicate to authenticate (i.e., validate) a user of the enterprisesystem and enable the validated user to access the resources andservices of the enterprise system.

In step 501, a first authentication request is initiated by a clientdevice, such as a mobile device 302 or 402. The first authenticationrequest may be login attempt by the client device 302 to the enterprisesystem, using a secured or unsecured application running on the clientdevice 302, for example, a console application, a mobile application, ora web browser or other web-based application. The user of the clientdevice 302 may input authentication credentials using an input interfaceand/or input device of the client device 302. For instance, the user mayuse a keyboard or touch screen to input a user identifier and passwordinto the client device 302, which may be encrypted and/or transmittedsecurely to an access gateway 360 of the enterprise system. The accessgateway 360 may be a secure server, and may be implemented as one ormore separate computing devices (as shown in FIGS. 3 and 4), oralternatively may be implemented within a server or other computingdevice providing resources or services (e.g., an email server, a webapplication server, etc.). The access gateway 360 may support variousadditional authentication techniques, such as password-based,token-based (e.g., smart cards, magnetic strip cards), biometrics (e.g.,fingerprint, voiceprint, iris or retina scanning), and the like. Theauthentication in step 501 may be single-factor or multi-factor, and mayinclude multiple authentication steps (e.g., challenge questions), andmutual authentication techniques.

In step 502, the authentication device 358 receives the authenticationrequest from the client device 302 and validates the user'sauthentication credentials to confirm that the user is a valid systemuser with permissions to access one or more resources or services of theenterprise system. In this example, the authentication device 358 mayrefer to a computing device(s) on which an authentication service 358executes. As illustrated in FIG. 3, an access gateway 360 may receivethe login request from the mobile device 302 and forward the loginrequest to an authentication service 358 which verifies the user'scredentials and grants the user access to the set of enterpriseresources or services for which the user is authorized. Theauthentication service 358 may be implemented on one or more dedicatedcomputing devices 358, on shared computing devices 358 that supportother enterprise services 308 and/or resources 304, or may beimplemented within the access gateway 360. In these examples, theauthentication device 358 may be configured to validate (i.e.,authenticate) users by presenting the credentials entered by the user toan authentication service, such as an active directory 422, which mayrule on their accuracy/validity of the user's credentials.

After the user's credentials have been successfully validated in step502, the user may be logged in to the enterprise system and may begranted access to resources 304 or services 308 within the enterprisesystem. The validation of the user in step 502 may be optional dependingon the design of the enterprise system. Additionally, in certainexamples, the user may be authorized to access some resources 304 andservices 308, but might not be authorized to access others, depending onthe user's permissions with respect to the various resources 304 andservices 308 in the enterprise system.

In this example, after the user is validated in step 502, the user maybe prompted in step 503 to input a “user secret” into the client device302 to be used in future resource access requests. In other examples,users may be prompted to input user secrets before, after, orcontemporaneously with the first authentication request in step 501 andvalidation in step 502. A “user secret” may be a personal identificationnumber (PIN), touch screen gesture, biometric data, spoken phrase orvisual image, or other data input into the client device 302 by theuser. In step 503, users may be allowed to select a user secret type(e.g., text, PIN, gesture, password, spoken phrase, biometric, etc.)before inputting their user secret. In other examples, the user secrettype may be selected automatically based on the physical capabilities ofthe client device 302, and the user may be prompted to input a usersecret of the selected type. For instance, if the client device 302 is amobile phone, PDA, or tablet computer with a touch screen, then the usermay be prompted to input a touch screen gesture as a user secret. If theclient device 302 includes a microphone and audio processing software,then the user may be prompted to speak a word or phrase as a usersecret. Similarly, if the client device 302 includes a camera, then theuser secret may be an image of the user's face, an item in the user'shome or office, or another object selected by the user. Other examplesof user secrets include text passwords input on keyboards, PINs input onkeyboards or numeric keypads, and/or may be derived from variousbiometric data (e.g., fingerprints, iris scans, etc.) or visual images,etc.

In some examples, user secrets may be different from and/or simpler thanthe authentication credentials (e.g., username and password) requiredfrom users to login to the enterprise system. Many systems requirestrong user passwords, such as passwords having a minimum length,complexity, and/or unpredictability. Such passwords can be tedious forusers to input, especially on devices such as mobile phones, PDAs, andtablet computers without traditional keyboards. In contrast, in someembodiments, the user secret may be permitted to be shorter and simplerthan the password, and thus quicker to input into the client device 302.Additionally, it may be optional or even required for a user to select auser secret that is different from the user's password input in step501. Therefore, if the user's secret is compromised (e.g., by malware atthe client device 302), then the user's password may remain protectedand the overall security of the enterprise system may be enhanced.

In step 503, software within the client device 302 and/or software withthe enterprise system may initiate a function to prompt the user of theclient device 302 to input a user secret. For example, theauthentication device 358 may initiate a function to prompt the user toinput a secret in response to the successful validation of the user'scredentials in step 502. In this example, the authentication device 358may first determine if a user secret has previously been set for clientdevice 302, and if not, may prompt the user to input a user secret. Theclient device 302 also may initiate a function to prompt the user toinput a user secret. For example, a receiver application 404 (or otherclient-based application 410) may suggest that the user input a usersecret in order to simplify future resource access requests to theenterprise system. The receiver 404 or other client application 410 mayfirst determine whether or not the user has previously input a usersecret, and/or may confirm with the user that the client device 302 isnot a shared device, before prompting the user to input a user secret.In some examples, a user secret may be received and transmittedcontemporaneously with the first authentication request. Thus steps 501and 503 may be combined into a single step, and similarly steps 502 and504 may be combined into a single step. Additionally, as discussed inmore detail below, user secrets may be optional and need not besupported in some embodiments, and thus steps 503 and 504 need not beperformed in some examples.

In step 504, the authentication device 358 in the enterprise system mayreceive the user secret from the client device 302, and may createvalidation data and an access token to be used for future resourceaccess requests from the client device 302. In some examples, the clientdevice 302 may initiate a call to the authentication service 358,passing into the authentication service the user secret input in step503. The client device 302 also may pass into the authentication service358 additional data confirming that the client device 302 is currentlylogged into the enterprise system, such as a session cookie or token.

The authentication device 358 may then create validation data, to bestored by the enterprise system (e.g., within the authentication device358, access gateway 360, or elsewhere within the enterprise system), andmay create an access token, to be transmitted to the client device 302in step 505. As discussed below, the access token and the validationdata may be used for future requests from the client device 302 to theenterprise system. In some embodiments, an access token may include acryptographic key (e.g., an encryption or decryption key) generated bythe authentication device 358 or received from a key generator, and thevalidation data may be created by the authentication device 358 usingthe cryptographic key to encrypt one or more of the following: a keyidentifier corresponding to the user and/or client device; the user'scurrent password or other authentication credentials; and the user'ssecret input in step 503. A key identifier may be a user identifier(e.g., username or login), or may be a separate identifier such as atable index used to locate the correct validation data.

Referring to FIG. 7A, an example is shown of creating validation data710 and an access token 705 by an authentication device 358 in step 504.In this example, the authentication device collects a key identifier 701(e.g., a username or table index corresponding to the user's validationdata), the user's password 702, and the user secret 703 input by theuser in step 503. The user's password 702 may include a password, token(e.g., a Security Assertion Markup Language (SAML) token), or usercredential data. The authentication device 358 encrypts this data usinga cryptographic key 705, which may be generated by the authenticationdevice 358 or received from encryption key generator within theenterprise system. The resulting encrypted data is the validation data710, which may be stored within the enterprise system in step 505 andmay be used to authenticate future requests from the user. Theauthentication device 358 in this example also creates an access token715 including the key identifier 701 and the cryptographic key 705 usedto encrypt the validation data 710. In step 505, the access token 715may be transmitted by the authentication device 358 to the client device302.

As shown in FIG. 7A, the validation data 710 may be generated byencrypting a key identifier 701, password 702, and user secret 703.However, in other examples, all three pieces of data need not be used,and the validation data 710 may be generated by encrypting only one ortwo of these pieces of data. The validation data 710 also may includecombination of encrypted and unencrypted data, or may be stored entirelyas unencrypted data in some examples. For instance, the validation data710 may be generated in some embodiments by appending the encryptedpassword 702 to an unencrypted key identifier 701. Similarly, the accesstoken 715 may include the cryptographic key 705 and user key 701, asshown in FIG. 7A, or alternatively may include only the cryptographickey 705. The access token 715 also may include additional information,such as data identifying multiple users associated with the access token715, one or more client applications associated with the access token715, a set of enterprises resources and/or services associated with theaccess token 715, and an access time period or expiration dateassociated with the access token 715.

In step 506, the client device 302 receives and stores the access token715 transmitted by the authentication device 358 in step 505. Asdiscussed above, the access token 715 may include anencryption/decryption key 705 without including an encrypted orunencrypted copy of the user's password 702 or secret 703. Accordingly,the access token 715 may be stored in a secure or unsecured memorywithin the client device 302.

In step 507, the user initiates a second authentication request to theenterprise system. Like the first authentication request, the secondauthentication request may be a login attempt to the enterprise systemand/or a request to access resources 304 or services 308 of theenterprise system. The second authentication request may be made via thesame client application used to make the first authentication request,or with a different client application. For instance, the firstauthentication request may be a login attempt made with a receiverapplication 404, and the second authentication request may be made by aseparate client application 410 (e.g., email client 410, web browser410, etc.) to access specific enterprise resources or services. Thesecond authentication request may occur shortly after the firstauthentication request (e.g., within the same network communicationsession), or may occur long after the first authentication request(e.g., after the expiration of any previous session cookies or tokens).

For the second authentication request, the client device 302 may promptthe user to input the user's secret, rather than the user's password (orother authentication credentials). As discussed above, the user's secretmay be shorter and simpler than the user's password, and thus may beeasier for the user to remember and quickly input at the client device302. Additionally, the user secret need not be a text string input via atraditional keyboard, but may be entered using another input interface,depending on the capabilities of the client device 302 and thepreferences of the user (e.g., a touch screen gesture, PIN, spokenphrase, or biometric data, etc.).

In step 508, the client device 302 retrieves the access token previouslystored in the device memory, and sends the second authenticationrequest, with the access token and the user secret input by the user instep 507, to the authentication device 358. For embodiments in whichuser secrets are not used, the second authentication request mightinclude the access token retrieved from the device memory, but not auser secret. Thus, although step 507 potentially may involve some useraction, for example, opening a client application 404 or 410, step 507need not involve prompting the user to input a user secret in certainembodiments. In such examples, the access token may be retrieved andsubmitted to the authentication device 358 without any explicit actionby the user, or even without the user's knowledge.

In step 509, the authentication device 358 receives the secondauthentication request from the client device 302. After receiving thesecond authentication request, the authentication device 358 mayretrieve the corresponding validation data for the client device 302,previously stored in step 504. For example, if the second authenticationrequest includes a key identifier 701, then the authentication device358 may use the key identifier 701 to look up and retrieve thevalidation data 710 corresponding to the user and/or client device 302.A key identifier 701 may be associated with a specific enterpriseuser/login, with a specific client device 302, or with a combination ofa user and a device. For instance, if a single user of the enterprisesystem has multiple client devices (e.g., a desktop computer, laptopcomputer, and one or more mobile devices), then each client device mayhave a separate key identifier 701 and/or a separate access token 715.Additionally, because the input types of user secrets may be based onthe capabilities of the client device (e.g., touch screen gestures,voice recognition, biometric input), it may be preferable for some usersto establish different user secrets for their different devices. Inthese examples, the authentication device 358 may use the key identifier701 and/or user secret 703 to look up and retrieve the appropriatevalidation data 710 that corresponds to the user and/or client device302 from which the second authentication request was received.

In step 510, the authentication device attempts to decrypt thevalidation data 710 using the access token 715 received in the secondauthentication request. As discussed above, a cryptographic key 705 thatmay be used to decrypt the validation data 710 was previouslytransmitted within the access token 715 to the client device 302 in step504. Therefore, if the same access token 715 is returned from the clientdevice in step 508, then the authentication device 358 may extract thekey 705 and successfully decrypt the validation data.

Referring to FIG. 7B, an example is shown of validating anauthentication request an authentication device 358, using a user secret703 and access token 715 received from a client device 302. In thisexample, after receiving the second authentication request from theclient device 302, the authentication device 358 may use the keyidentifier 701 to identify the user and retrieve the appropriatecorresponding validation data 710 from the memory of the enterprisesystem. The authentication device 358 may then extract the key 705 fromthe authentication request and use the key 705 to decrypt the validationdata 710. If the decryption is successful, the authentication device 358may compare the user secret 703 from the decrypted validation data, withthe user secret 703 received from the client device 302 with therequest. If the user secrets match, the authentication device 358 mayconclude that the user secret 703 and the access token 715 are valid,and thus the second authentication request is a valid request from thesame user that was successfully validated in step 502. In embodiments inwhich a user secret 703 is not used, the authentication device 358 mayconclude that the second authentication request is valid based on thevalidation of the decryption using the access token 715, without needingto validate a user secret 703.

In the examples shown in FIGS. 7A and 7B, the user secret 703 is storedwithin the validation data 710. However, in other examples, the usersecret need not be stored within the validation data 710. For instance,the validation data 710 may be used to construct the access token 715(or part of the access token 715). In certain embodiments, the keyidentifier 701, a user identifier, and/or a user password or token 702may be encrypted with the cryptographic key 705 to create the validationdata 710. Then, the access token 715 may be created using the keyidentifier 701 and the output of a comingling function (e.g., anexclusive OR function) performed on the key 705 and the user secret 703.In such examples, when validating the authentication request(corresponding to step 510 and FIG. 7B), the authentication device 358may retrieve the user secret from a storage within the enterprisesystem, and may use the user secret to perform a reverse cominglingfunction on the access token 715, which may return the cryptographic key705. The authentication device 358 may then use the key identifier 701to retrieve the corresponding validation data 710 from storage, and mayuse the key 705 to decrypt the validation data 710, thereby providingthe user identifier and/or user password or token 702.

Even if the user secret 703 and the access token 715 received from theclient device 302 are valid, the authentication device 358 might notgrant the user access to the requested resources if the user's password702 has been changed or has expired. For example, after confirming thevalidity of the user secret 703 and access token 715 received from theclient device 302, the authentication device 358 may be configured tocommunicate with a domain controller, active directory, or other serviceto confirm that the user's password 702 in the validation data 710 isstill up to date and valid. If the user's password 702 has expired, thenthe authentication device 358 may initiate a function prompting the userto enter a new password for the enterprise system, after which theauthentication device 358 may update the user's password within thesystem and also may create new validation data 710 with the new password702. After changing the user's system password 702, the authenticationdevice 358 also may require the user to create a new user secret 703, oralternatively may allow the user to keep the same user secret 703.

The authentication device 358 also may determine that the user'spassword 702 is no longer valid, for example, because the user hasrecently logged into the enterprise system using a different clientdevice and changed their password 702. In this case, after confirmingthat the user secret 703 and the access token 715 are valid, but thatthe password 702 is not valid, the authentication device 358 may requireto user to re-authenticate on the client device 302 with the user'scurrent password. After the user re-authenticates, the authenticationdevice 358 may create new validation data 710 with the new password 702.The authentication device 358 may optionally require the user to input anew secret 703, and may optionally create and transmit a new accesstoken 715 to the client device 302.

As noted above, user secrets may be optional in some embodiments. Insuch cases, the validation data encrypted by the authentication device358 may include only a key identifier and/or password for the userauthenticated in step 502. Thus, the user need not input a user secretin step 503, or in step 507 before sending the second authenticationrequest. When a user secret is not used, the access token may be createdby the authentication device 358 automatically, and then transmitted tothe client device 302 after the first successful authentication request.The access token then may be stored on the client device 302, andretrieved and transmitted in subsequent authentication requests back tothe enterprise system, without any explicit action taken from the user(and possibly without the user even knowing that access tokens are beingused). Additionally, in certain embodiments, user secrets may be enteredby the user (e.g., in steps 503 and/or 507), but may or may not be usedby the authentication device 538, depending on the resources andservices requested. A user may establish a user secret in step 503, butthe authentication device 538 might require the user to reenter the usersecret in step 507 only to access certain resources and/or performcertain actions, but not for others. For instance, a user secret mightnot be required in order for the user to read email or access certainsecure documents, but may be required to send emails or modify thesecure documents.

In some cases, access tokens and/or user secrets may have associatedtime periods or expiration dates, which may be stored within theenterprise system. In such cases, the authentication device 358 mayretrieve the associated time period or expiration date after receivingan authentication request containing an access token. If the accesstoken is valid and has not yet expired, the user may be granted accessto the requested resources or services of the enterprise system.However, if the access token received from the client device 302 hasexpired or is no longer valid, then the authentication device 358 mayrequire the user to re-enter the user's full authentication credentials(e.g., username and password), at which time the access token may bereset for an additional time period. In some embodiments, the user maybe required to enter a new and different user secret after theexpiration of a previous access token on the client device 302.Additionally, access tokens may be explicitly revoked by theauthentication device 358 and/or client device 302. For example, accesstokens may be revoked by the authentication device 358 by removing (ormarking as revoked) the associated validation data entries. Lists ofusers or devices also may be stored in the enterprise system for whomthis access method is not permitted.

Certain access tokens and/or user secrets also may be associated withspecific resources or services within the enterprise system. Forexample, an access token stored on the client device 302 may besuccessfully validated when the user requests access to a firstenterprise resource 304, but the same access token may be rejected whenthe user requests access to a different enterprise resource 304. In thisexample, the authentication device 358 may store a list of enterpriseresources or services corresponding to each access token/validation datapair. When the authentication device 358 receives a request forenterprise resources or services with an access token, theauthentication device 358 may retrieve the list of enterprise resourcesassociated with the access token, and may grant or deny the requestaccordingly.

Therefore, in some examples, multiple different access tokens may becreated for and stored on a single client device 302. For instance, afirst access token may be valid for requests for certain enterpriseresources 304 or services 308, while a second access token may be validfor requests for other enterprise resources 304 or services 308, and soon. In this example, the client application (e.g., receiver 404 orapplication 410) may retrieve and transmit the correct access token fromthe memory of the client device 302 depending on the resourcesrequested. Because some client applications, such as web browser 410 oremail client 410, may be associated with specific enterprise resources,these client applications 410 may be configured to retrieve and transmita particular access token for all requests. In other cases, a clientapplication may identify the specific resources 304 or services 308being requested by the user, and the correct access token may then beretrieved from the device memory. Further, if a single client device(e.g., desktop computer or mobile device) is shared by multiple users,then multiple access tokens (or multiple sets of access tokens) may bestored in the memory of the client device 302. In these examples, theclient application (e.g., receiver 404 or application 410) may beconfigured to retrieve and transmit the access token associated with thecurrent user of the device.

Referring now to FIG. 6, an example method is shown in which a clientdevice (e.g., mobile device 302 and/or 402), an access gateway (e.g.,access gateway 360 and/or cloud gateway 406), an authentication service358, and an enterprise resource or service (e.g., resources 304 and/orservices 308 or 408) may interact to validate a user with a first set ofauthentication credentials to an enterprise resource 304 or service 308accepting a second set of authentication credentials.

In step 601, a user at a client device 302 initiates a login request tothe enterprise system including a first set of authenticationcredentials. The login request in step 601 may be similar to the firstauthentication request (step 501) described above in FIG. 5. Asdescribed above, the login request may be transmitted from the clientdevice 302 via a client application such as a receiver 404 or otherapplication 410 (e.g., email client, web browser, etc.). The loginrequest in step 601 may include a first set of authenticationcredentials, for example, a username and password, data from a smartcard, biometric data, or other type of user authentication data. Thefirst set of authentication credentials also may be similar to theauthentication credentials transmitted in step 508 of FIG. 5, forexample, including a user secret 703 and/or access token 715.

In step 602, the login request may be received by an access gateway 360.The access gateway 360 may determine that the request is a new requestfrom a client device 302, for example, it may determine that the requestis not part of an existing communication session with an enterpriseresource 304 or service 308. After determining that the request is alogin request, the access gateway 360 may route the login request andauthentication credentials to an authentication service 358 to validatethe credentials and determine whether or not the user is authorized tologin to the enterprise system. Although the authentication in thisexample may be performed via the access gateway 360, in other examplesthe authentication need not be performed via the gateway 360.

In step 603, the authentication service 358 receives and validates thefirst set of authentication credentials, to confirm that the user is avalid user and is authorized to login to the enterprise system. Thevalidation in step 603 may be similar to the validation of the firstauthentication request (step 502) described above in FIG. 5. In order tovalidate the user in step 603, the authentication service 358 may beconfigured to access a secure data storage or service within theenterprise system, such as an active directory or domain controller, toverify the first set of user authentication credentials. Aftersuccessfully validating the user with the first set of credentials instep 603, the user may be logged in to the enterprise system and may begranted access to various resources 304 or services 308 of theenterprise system.

Additionally, after validating the user with the first set ofcredentials in step 603, the authentication service 358 may beconfigured to retrieve one or more additional sets of credentials forthe same user in step 604. Within the enterprise system, a single usermay have multiple different authentication credentials corresponding todifferent enterprise resources 304 and services 308. For example, a usermay have a first set of credentials (e.g., username and password) tologin to the enterprise system, a second set of credentials to login tothe user's email server 304, a third set of credentials to access aweb-based application on a web application server 304, a fourth set ofcredentials to invoke a file sharing service 368, and so on. Thus, instep 604, the authentication service 358 may access various enterpriseservices and resources, such as an active directory, a domain controllerservice, and/or a user credential database. The authentication service358 also may initiate communication with individual enterprise services308 and resources 304 (e.g., Exchange, Sharepoint, PKI Resources,Kerberos Resources, Certificate Issuance, etc.) in order to retrieve theauthentication credentials of the same user for these individualservices and resources.

After retrieving the additional sets of credentials for the user in step604, the authentication service 358 may transmit the additional sets ofcredentials to the access gateway 360. In step 605, the access gateway360 may receive and store the additional sets of credentials for theuser in a memory within the gateway 360 or other storage accessible tothe gateway 360. In some embodiments, the user's additional sets ofcredentials may be stored securely within the gateway 360 and/or may bestored external to the gateway 360 to provide additional security forthe enterprise system, in the event that the gateway 360 is compromised.In the example shown in FIG. 6, steps 604 and 605 may be performed inresponse to a successful user validation in step 603. In other examples,the retrieval and storage of additional credentials in step 604 and 605may be performed at later time. For instance, steps 404 and 405 may beperformed after step 606, in response to a request by the access gateway360 to the authentication server 358 for the secondary credentials.

The additional sets of user credentials stored in 605 also may beencrypted, for example, in the form of the validation data 710 describedabove in reference to FIG. 5. In such examples, the sets ofauthentication credentials for different users may be encrypted usingdifferent cryptographic keys 705. As described above, these differentkeys 705 may be transmitted in access tokens 715 to the client devices302 of the different users. Thus, if a user's key 705 is compromised bya malicious party with access to the authentication credentials storedon the gateway 360, then the malicious party could only decrypt thepasswords/credentials of that user, and could not decrypt thepasswords/credentials of other users which were encrypted with differentkeys 705.

In step 606, the user at a client device 302 initiates a request to anenterprise resource 304 or service 308 within the enterprise system,using the same first set of credentials used for the login request instep 601. The request in step 606 may be another login request and/or arequest for data or services from a resource 304 or service 308 in theenterprise system, for example, an email server 304, file sharing server304, web application server 304, device manager service 324, filesharing service 368, social integration service 372, or any otherresource or service provided by the enterprise system.

In step 607, the access gateway 360 may receive and validate the user'sfirst set of credentials, and then may inject a second different set ofcredentials into the request before routing the request to theappropriate resource 304 or service 308. After receiving the requestfrom the client device 302, the access gateway 360 may validate theuser's first set of credentials to confirm that the user is a validsystem user with permissions to access the requested resource 304 orservice 308. The user validation in step 607 may be similar to thevalidation by the authentication service 358 described above in any ofsteps 603, 502, and/or 510. For example, the access gateway 360 mayverify the user's authentication credentials by comparing them to theuser credentials stored at the gateway 360 in step 605, or within asecure data storage or service within the enterprise system, such as anactive directory or domain controller. In other cases, the uservalidation in step 607 may be performed using a token/cookie, ratherthan by validation of the first credentials. For example, after a firstvalidation of user credentials in steps 601-603, the access gateway 360may return a session token or cookie to the client device 302. In step606, the client device 302 may use the session token or cookie in lieuof the first credentials, and in step 607 the access gateway may confirmthat the received token or cookie was issued by the gateway 360 and isstill current.

After verifying that the user is authorized to access the requestedresource 304 or service 308, the access gateway 360 may determine if therequested resource 304 or service 308 will accept the first set ofauthentication credentials entered by the user in step 606. As discussedabove, a single user may have multiple different authenticationcredentials for the different resources 304 and services 308 in theenterprise system. If the requested resource 304 or service 308 will notaccept the user's first set of authentication credentials, then theaccess gateway 360 may retrieve and inject the appropriate set of theauthentication credentials into the request. For instance, if the user'sfirst set of authentication credentials are the user's enterprise systemusername and password, or are a access token 715 and a previouslyentered user secret 703, then the requested resource 304 or service 308(e.g., email server, web application server, etc.) may not accept theseuser authentication credentials. Thus, in step 607, the access gateway360 may retrieve a second set of valid user credentials from theauthentication credentials stored in step 605, and may inject the secondset of credentials into the request before forwarding the request to theresource 304 or service 308.

In step 608, the requested enterprise resource 304 or service 308receives and validates the request from the access gateway 360. Sincethe access gateway 360 injected the second set of valid user credentialsinto the request, the resource 304 or service 308 may successfullyverify the user using the second set of credentials just as though thecredentials had been entered directly by the user at the client device302. The validation in step 608 may involve multiple authenticationsteps and/or one or more challenge-response verifications. However,because the access gateway 360 has the request from the client device302 and the proper authentication credentials for the user to access theresource 304 or service 308, the gateway 360 may handle allauthentication challenges without the involvement of the user or theclient device 302.

After the resource 304 or service 308 validates the user with the secondset of credentials in step 608, the requested data and/or services maybe provided by the resource 304 or service 308 to the validated user instep 609. In step 610, the access gateway 360 receives the requesteddata and/or services from the enterprise resource or service, andforwards the data to the client device 302, and, in step 611, the clientdevice 302 receives and provides the requested data and/or services tothe user.

Thus, in this example, the access gateway 360 may act as a proxy serverbetween the client device 302 and the requested resource 304 or service308. That is, because the access gateway 360 validates the first set ofuser credentials, and then retrieves and injects the second set of usercredentials in the request, it may appear to the client device 302 thatthe first set of credentials are being submitted to the resource 304 orservice 308, and it may appear to the resource 304 or service 308 thatthe correct second set of credentials were provided by the user at theclient device 302. A user at the client device 302 may thus use a singleset of authentication credentials to successfully login to multipledifferent resources 304 and services 308 that require different sets ofthe credentials. This functionality may be transparent to the user, sothat the user need not know the correct authentication credentials formany different resources 304 and services 308, but may nonethelessaccess these different resources 304 and services 308 with a singlesign-on using a single set of authentication credentials. Moreover, whenonly a single set of authentication credentials are known to the user,and are stored and transmitted by the client device 302, this single setof credentials might not include a secure password or any otherenterprise system authentication data. For example, as discussed above,the first set of authentication credentials may be a user secret 703and/or access token 715 including a key 705 that may be used to decryptone or more encrypted passwords for the user.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are described asexample implementations of the following claims.

1-20. (canceled)
 21. A method comprising: receiving, by a computingsystem associated with an enterprise mobility-management computingenvironment and from a client device associated with a user of theenterprise mobility-management computing environment, authenticationcredentials for a resource of the enterprise mobility-managementcomputing environment; and responsive to authenticating the clientdevice with the resource based on the authentication credentials:storing, by the computing system, validation data comprising theauthentication credentials and an identifier corresponding to at leastone of the client device or the user; generating, by the computingsystem, an access token for the enterprise mobility-management computingenvironment comprising the identifier and a key utilized by thecomputing system to encrypt the authentication credentials; andcommunicating, by the computing system and to the client device, theaccess token for subsequent authentication of the client device with theenterprise mobility-management computing environment based on theidentifier, the key, and the validation data.
 22. The method of claim21, comprising, responsive to receiving, by the computing system, datagenerated by the client device comprising the access token and a requestto access the resource: identifying, by the computing system, thevalidation data based on a portion of the data generated by the clientdevice comprising the identifier; decrypting, by the computing system,the authentication credentials using a portion of the data generated bythe client device comprising the key; and authenticating, by thecomputing system, the request using the authentication credentials. 23.The method of claim 22, comprising, prior to receiving the request,updating, by the computing system, the validation data based on amodification to the authentication credentials indicated by datareceived by the computing system from a different client deviceassociated with the user, wherein authenticating the request comprisesauthenticating the request based on the modification.
 24. The method ofclaim 21, comprising, responsive to receiving, by the computing system,data generated by the client device comprising the access token and arequest to access a different resource of the enterprisemobility-management computing environment: identifying, by the computingsystem, the validation data based on a portion of the data generated bythe client device comprising the identifier; decrypting, by thecomputing system, authentication credentials for the different resourceusing a portion of the data generated by the client device comprisingthe key; and authenticating, by the computing system, the request usingthe authentication credentials for the different resource.
 25. Themethod of claim 24, comprising, prior to receiving the request:receiving, by the computing system and from a different client deviceassociated with the user, the authentication credentials for thedifferent resource; and responsive to authenticating the differentclient device with the resource based on the authentication credentialsfor the different resource, updating, by the computing system, thevalidation data to include the authentication credentials for thedifferent resource.
 26. The method of claim 24, comprising, prior toreceiving the request and responsive to a determination by the computingsystem that the user is authorized to utilize the different resource:receiving, by the computing system, from the different resource, andresponsive to a request generated by the computing system, theauthentication credentials for the different resource; and updating, bythe computing system, the validation data to include the authenticationcredentials for the different resource.
 27. The method of claim 21,wherein the validation data comprises authentication informationdistinct from the authentication credentials, received by the computingsystem from the client device, and input by the user via the clientdevice in response to a prompt generated by the computing system via theclient device, the method comprising, responsive to receiving, by thecomputing system, data generated by the client device comprising theaccess token and a request to access a different resource of theenterprise mobility-management computing environment: identifying, bythe computing system, the validation data based on a portion of the datagenerated by the client device comprising the identifier; decrypting, bythe computing system, authentication credentials for the differentresource using a portion of the data generated by the client devicecomprising the key; and responsive to determining that a portion of thedata generated by the client device comprises the authenticationinformation, authenticating, by the computing system, the request usingthe authentication credentials for the different resource.
 28. A systemcomprising: at least one processor; and a memory comprising instructionsthat when executed by the at least one processor cause the system to:receive, from a client device associated with a user of an enterprisemobility-management computing environment, authentication credentialsfor a resource of the enterprise mobility-management computingenvironment; and responsive to authenticating the client device with theresource based on the authentication credentials: store validation datacomprising the authentication credentials and an identifiercorresponding to at least one of the client device or the user; generatean access token for the enterprise mobility-management computingenvironment comprising the identifier and a key utilized by the systemto encrypt the authentication credentials; and communicate, to theclient device, the access token for subsequent authentication of theclient device with the enterprise mobility-management computingenvironment based on the identifier, the key, and the validation data.29. The system of claim 28, wherein the instructions, when executed bythe at least one processor, cause the system to, responsive to receivingdata generated by the client device comprising the access token and arequest to access the resource: identify the validation data based on aportion of the data generated by the client device comprising theidentifier; decrypt the authentication credentials using a portion ofthe data generated by the client device comprising the key; andauthenticate the request using the authentication credentials.
 30. Thesystem of claim 29, wherein the instructions, when executed by the atleast one processor, cause the system to: prior to receiving therequest, update the validation data based on a modification to theauthentication credentials indicated by data received by the system froma different client device associated with the user; and authenticate therequest based on the modification.
 31. The system of claim 28, whereinthe instructions, when executed by the at least one processor, cause thesystem to responsive to receiving data generated by the client devicecomprising the access token and a request to access a different resourceof the enterprise mobility-management computing environment: identifythe validation data based on a portion of the data generated by theclient device comprising the identifier; decrypt authenticationcredentials for the different resource using a portion of the datagenerated by the client device comprising the key; and authenticate therequest using the authentication credentials for the different resource.32. The system of claim 31, wherein the instructions, when executed bythe at least one processor, cause the system to: receive, from adifferent client device associated with the user, the authenticationcredentials for the different resource; and responsive to authenticatingthe different client device with the resource based on theauthentication credentials for the different resource, update thevalidation data to include the authentication credentials for thedifferent resource.
 33. The system of claim 31, wherein theinstructions, when executed by the at least one processor, cause thesystem to, prior to receiving the request and responsive to adetermination by the system that the user is authorized to utilize thedifferent resource: receive, from the different resource and responsiveto a request generated by the system, the authentication credentials forthe different resource; and update the validation data to include theauthentication credentials for the different resource.
 34. The system ofclaim 28, wherein the validation data comprises authenticationinformation distinct from the authentication credentials, received bythe system from the client device, and input by the user via the clientdevice in response to a prompt generated by the system via the clientdevice, and wherein the instructions, when executed by the at least oneprocessor, cause the system to, responsive to receiving data generatedby the client device comprising the access token and a request to accessa different resource of the enterprise mobility-management computingenvironment: identify the validation data based on a portion of the datagenerated by the client device comprising the identifier; decryptauthentication credentials for the different resource using a portion ofthe data generated by the client device comprising the key; andresponsive to determining that a portion of the data generated by theclient device comprises the authentication information, authenticate therequest using the authentication credentials for the different resource.35. One or more non-transitory computer-readable media comprisinginstructions that when executed by one or more computers cause the oneor more computers to: receive, from a client device associated with auser of an enterprise mobility-management computing environment,authentication credentials for a resource of the enterprisemobility-management computing environment; and responsive toauthenticating the client device with the resource based on theauthentication credentials: store validation data comprising theauthentication credentials and an identifier corresponding to at leastone of the client device or the user; generate an access token for theenterprise mobility-management computing environment comprising theidentifier and a key utilized by the one or more computers to encryptthe authentication credentials; and communicate, to the client device,the access token for subsequent authentication of the client device withthe enterprise mobility-management computing environment based on theidentifier, the key, and the validation data.
 36. The one or morenon-transitory computer-readable media of claim 35, wherein theinstructions, when executed by the one or more computers, cause the oneor more computers to, responsive to receiving data generated by theclient device comprising the access token and a request to access theresource: identify the validation data based on a portion of the datagenerated by the client device comprising the identifier; decrypt theauthentication credentials using a portion of the data generated by theclient device comprising the key; and authenticate the request using theauthentication credentials.
 37. The one or more non-transitorycomputer-readable media of claim 36, wherein the instructions, whenexecuted by the one or more computers, cause the one or more computersto: prior to receiving the request, update the validation data based ona modification to the authentication credentials indicated by datareceived by the one or more computers from a different client deviceassociated with the user; and authenticate the request based on themodification.
 38. The one or more non-transitory computer-readable mediaof claim 35, wherein the instructions, when executed by the one or morecomputers, cause the one or more computers to responsive to receivingdata generated by the client device comprising the access token and arequest to access a different resource of the enterprisemobility-management computing environment: identify the validation databased on a portion of the data generated by the client device comprisingthe identifier; decrypt authentication credentials for the differentresource using a portion of the data generated by the client devicecomprising the key; and authenticate the request using theauthentication credentials for the different resource.
 39. The one ormore non-transitory computer-readable media of claim 38, wherein theinstructions, when executed by the one or more computers, cause the oneor more computers to: receive, from a different client device associatedwith the user, the authentication credentials for the differentresource; and responsive to authenticating the different client devicewith the resource based on the authentication credentials for thedifferent resource, update the validation data to include theauthentication credentials for the different resource.
 40. The one ormore non-transitory computer-readable media of claim 38, wherein theinstructions, when executed by the one or more computers, cause the oneor more computers to, prior to receiving the request and responsive to adetermination by the one or more computers that the user is authorizedto utilize the different resource: receive, from the different resourceand responsive to a request generated by the one or more computers, theauthentication credentials for the different resource; and update thevalidation data to include the authentication credentials for thedifferent resource.